Populating a Database in a Communication System

ABSTRACT

A method of populating a store with information identifying user devices capable of communicating in a communications network, includes establishing a communication event from an initiator device to a recipient device via the communication network using information identifying the recipient device; receiving from a user of the initiator device a selection signal indicating that said information identifying the recipient device is to populate the store; and transmitting said information identifying the recipient device from the initiator device to the store via the communication network.

RELATED APPLICATION

This application claims priority under 35 U.S.C. §119 or 365 to Great Britain, Application No. GB 0624577.3, filed Dec. 8, 2006. The entire teachings of the above application are incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to a method and system for storing data relating to a called party in a communication system. In particular the invention relates, but not exclusively to storing called party data in a communication system.

BACKGROUND

In a communication system a communication network is provided, which can connect two communication terminals so that the terminals can send information to each other in a call or other communication event. Information may include voice, text, images or video.

Protocols which are used to carry voice signals over the internet are commonly referred to as Voice over Internet Protocol (VoIP) and may also be referred to as Voice over Broadband. VoIP is the protocol used for routing of voice conversations over the Internet or through any other IP-based network.

One such communication system to use VoIP is a peer to peer communication system, in which a plurality of end users can be connected for communication purposes via a communications structure such as the internet. A peer to peer network may also use other protocols to facilitate the transfer of other data such as text images or video. The communications structure is substantially decentralised with regard to communication route switching therein for connecting the end users. That is, the end users can establish their own communication routes through the structure based on exchange of one or more authentication certificates (user identity certificates—UIC) to acquire access to the structure. The structure includes an administration arrangement issuing the certificates to the end users. Such a communication system is described in WO 2005/009019.

In a communication system, such as a peer to peer system, client software is installed on end user devices such as personal computers (PCs) to allow the end users to communicate via the communications network. The user interface of the client software can be controlled by the client to display user facilities and to indicate events occurring, such as an incoming call.

When making a voice call or setting up another type of communication with a user device the user may either manually input a number identifying the called party or recall a number that has been pre-stored in a list of contacts on the client by the user. If the user does not know the number it is necessary for the user to look up the number possibly using a number look up service before initiating the call.

When making a call to a number that has not been pre-stored by the user, the user may be required to look up the same number more than once if he does not remember to save the number in his list of contacts, or to record the number by other means for example in an address book.

It is therefore an aim of embodiments of the invention to address at least one of the above identified problems.

SUMMARY

According to a first aspect of the present invention there is provided a method of populating a store with information identifying user devices capable of communicating in a communications network, the method comprising: establishing a communication event from an initiator device to a recipient device via the communication network using information identifying the recipient device; receiving from a user of the initiator device a selection signal indicating that said information identifying the recipient device is to populate the store and transmitting said information identifying the recipient device from the initiator device to the store via the communication network.

According to a second aspect of the present invention there is provided a method of storing information relating to a plurality of user devices capable of communicating in a communications network on a store, the method comprising;

inputting to the store information necessary to establish communication with the plurality of user devices via the communications network; generating call statistics relating to the number of communication events occurring with the plurality of user device across the communications network; inputting to the store information relating to the call statistics for the plurality of user devices.

According to a third aspect of the present invention there is provided a method of storing the number of communication events initiated by initiating nodes in a first network to a receiving node in a second network comprising; transmitting information from an initiating node in the first network to the receiving node in the second network via a gateway; monitoring the information transmitted via the gateway to the receiving node; determining the number of communication events received at the receiving node from the information transmitted via the gateway; and storing the number of communication events received by the receiving node in a data store.

According to a fourth aspect of the present invention there is provided a method of communicating in a communication network using communication information stored on a data store by a plurality of users comprising; inputting searching criteria to search the data store by a first user; retrieving a set of information from the data store corresponding to the searching criteria; determining if any information in the set was stored on the data store by a user associated with the first user; displaying any information that was determined as being updated by a user associated with the first user, to the first user; initiating a communication event by the first user to a second user using the information presented to the first user.

According to a fifth aspect of the present invention there is provided a communication system comprising; a store arranged to store information identifying a plurality of devices capable of communicating in the communication system; and an initiator device arranged to initiate a communication event to a recipient device via the communication system using information identifying the recipient device, wherein the initiator device comprises; receiving means arranged to receive from the user of the initiator device a selection signal indicating that the information identifying the recipient device is to populate the store; and transmitting means arranged to transmit said information identifying the recipient device to the store via the communication system.

According to a sixth aspect of the present invention there is provided an initiator device arranged to initiate a communication event to a recipient device in a communication network comprising; input means for inputting information identifying the recipient device to initiate the communication event; receiving means arranged to receive from the user of the initiator device a selection signal indicating that the information identifying the recipient device is to populate the store; and transmitting means arranged to transmit said information identifying the recipient device to the store via the communication network.

According to a seventh aspect of the present invention there is provided a computer program product comprising program code means which when executed on an initiator device implement the steps of; establishing a communication event from the initiator device to a recipient device via a communication network using information identifying the recipient device; receiving from a user of the initiator device a selection signal indicating that said information identifying the recipient device is to populate a store; transmitting said information identifying the recipient device from the initiator device to the store via the communication network.

According to an eighth aspect of the present invention there is provided a database comprising a plurality of data entries relating to user devices capable of communicating in a communications network, wherein each entry comprises; information necessary to establish a communication with a user device via the communications network; and information relating to the number of communication events occurring with the user device across the communications network.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention and to show how the same may be carried into effect, embodiments of the present invention will now be described with reference to the following drawings:

FIG. 1 is a schematic representation of a peer to peer communication system in accordance with an embodiment of the present invention;

FIG. 2 shows a client stack;

FIG. 3 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 4 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 5 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 6 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 7 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 8 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 9 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 10 shows a page displayed by the client user interface in accordance with an embodiment of the present invention;

FIG. 11 shows an arrangement for measuring call statistics in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

Reference will first be made to FIG. 1, in which is shown a communication system 100, including a packet switched network such as a peer to peer network 104 such as the internet. The communication system may also include a circuit switched networks such as PSTN (Public Switched Telephone Networks) (not shown). It should be appreciated that even though the exemplifying communications network shown and described in more detail uses peer to peer and PSTN networks, embodiments of the present invention can be used in any other suitable form of network.

A user device 102 is shown connected to the peer to peer network 104. The user device 102 may be, for example, a personal computer, a gaming device, a personal digital assistant, a suitably enabled mobile phone or other device able to connect to the network 104. The user device has a user interface means to receive information from and output information to a user of the device. In a preferred embodiment of the invention the interface means of the user device comprises a display means such as a screen and a keyboard or mouse. The user device 102 is connected to the network 104 via a network port 105, and may be via a cable (wired) connection or a wireless connection. The network 104 may be a network such as the Internet.

In accordance with an embodiment of the invention the network communication system includes a data store 126 that stores data relating to a called party. In one embodiment of the invention the data store 126 may be provided on at least one server.

If the user device is connected to the network 104, then it may be running a client program 112 provided by the operator of the peer-to-peer system. The client 112 is a software program executed on a local processor in the user device 102. The client 112 has a number of different components or layers for implementing various functions, including a protocol layer 402 (FIG. 2) for managing the network interface.

Also connected to the network 104 are a backend server 122 and a web application 124. The backend server 122 and the web application 124 may be located within the private network 128 of the operator of the communication system. The backend server 122 and the web application 124 may be geographically co-located, or may be geographically separated. The backend server 122 is located between the web application 124 and the network 104, and is responsible for exchanging messages between the web application 124 and the client 112. The backend server is also responsible for storing a contact list for the client that includes a list of other users of the network that the client 112 has previously stored as contacts. The backend server 122 and the client software may communication using a protocol described in our UK Application Number 0608752.2.

FIG. 2 shows a protocol stack for the client 112 according to an embodiment of the present invention. The protocol stack shows an operating system layer 401, a protocol layer 402, a client engine layer 404 and a client user interface layer 406. Each layer is responsible for specific functions. Because each layer usually communicates with two other layers, they are regarded as being arranged in a stack as shown in FIG. 2. The operating system layer 401 manages the hardware resources of the computer and handles data being transmitted to and from the network. The client protocol layer 402 of the client software communicates with the operating system 401. Processes requiring higher level processing are passed to the client engine layer 404. The client engine 404 also communicates with the user client user interface layer 406. The client engine may be arranged to control the client user interface layer 406 to present information to the user via the user interface means and to receive information from the user via the user interface means. The control of the client user interface 406 will be explained in more detail hereinafter.

A calling user 106 of the user device 102 can communicate with a called user 108 of a user device 110 across the network 104. In one embodiment of the invention the client interface is arranged to display a page, on a display provided by the user interface means of the user device 102, to enable the user to initiate the communication. The page may list pre stored call data for a plurality of users, otherwise referred to as a list of contacts that correspond to the contact list stored on the backend server 122. To initiate the communication, the calling user 106 can click on the contact listed for the user 108. Alternatively the calling user 106 can input an identity for the called user, such as a telephone number for the user device 110, or a username for the user 108 into the user device 102, using either a keyboard or a mouse to select alphanumeric buttons displayed on the screen. The client then sets up the call to the called user 108. The call may be made using VoIP, in accordance with methods known in the art, such as disclosed in WO 2005/009019. The communication may comprise voice, video, instant messaging (“IM”), short message service (SMS) or a combination thereof.

FIG. 1 shows the called user device 110 connected directly to the peer to peer network 104. In an alternative embodiment the called user device 110 may be connected to a different network such as the public switched telephone network (“PSTN”) or a mobile network (not shown in FIG. 1). If connected to the PSTN, the called user device 110 may be a fixed line telephone, and if connected to a mobile network, the called user device 110 may be a mobile telephone.

The communication between the calling user device 102 and the called user device 110 may be terminated by either the calling user 106 or the called user 108. If the call is terminated by the called user of the user device 110, the client protocol layer 402 of the client running on the calling user device 102 receives notification from the network that the call has been terminated and controls the client engine 404 accordingly. Conversely if the calling user of the user device 102 terminates the call, the client engine 404 of the client running on the calling user device 102 may receive an instruction from the client user interface 406 to terminate the call and will control the client protocol layer 402 to terminate the network connection.

When a call is terminated, the client engine 404 controls the client user interface 406 to display a notification to the calling user that the call is terminated. The notification may include a timer indicating the duration of the call.

In accordance with an embodiment of the invention the client engine may also be arranged to control the client user interface to display a selectable option that allows the calling user to save the details of the called user 108 on the data store 126 when the call is terminated. The page 300 as shown in FIG. 3, described hereinafter, is one example of how the client user interface may display a selectable option that allows the calling user to save the details of the called user.

In an alternative embodiment of the invention the client engine may be arranged to control the client user interface to allow the calling user 106 to save the details of the called user 108 that he is in communication with during the call. In this embodiment of the invention the client user interface may prompt the calling user to input details relating to the called user 108, immediately after connection or a predetermined time after connection.

In a further alternative embodiment of the invention, the client user interface may be arranged to allow the user to input details of another user to be saved on the data store 126 at anytime.

In accordance with an embodiment of the present invention the details of the called user will include the information necessary to establish a connection via the communication system 100 with the called user device 110. The details may also include the postal address of the called user. The information required to contact the called user will hereinafter be referred to as the contact details of the user.

FIG. 3 shows a page 300 that may be displayed on a display screen of the user device 102 by the client user interface when the call has been terminated according to a preferred embodiment of the present invention.

Pages displayed on the display screen may be implemented, for example, using HTML (Hyper Text Markup Language) or code that is specific to the client software 112.

The page 300 displays the identity of the called user 108, such as the telephone number of the called user device 110. According to an embodiment of the invention the client user interface is also arranged to provide a means for storing the called user data in the data store 126. In a preferred embodiment of the invention the page 300 displays a selectable link 301 that the user may select to indicate to the client software that the called user information should be stored to the data store 126.

In an alternative embodiment of the invention the calling user may select a key on a keyboard or other alternative input device, in order to indicate to the client software that the called user data should be stored on the data store 126.

In one embodiment of the invention the client 112 may be arranged detect a language setting preset by the user, and to only provide means for allowing a user to store called user information on the data store if the language is set to an admissible language. In one embodiment an admissible language is one that uses the Roman alphabet.

When the calling user selects the link 301 the client engine 404 may control the client user interface 406 to allow the details relating to the user 108 to be input. In accordance with an embodiment of the invention, contact information used to establish the call between user device 102 and user device 110 may be stored in a local memory of the user device 102. When the user selects the link 301 to indicate that the called user details are to be saved, the client 112 is arranged to retrieve the contact information from the memory so that the user is not required to manually enter the information again.

FIG. 4 shows a page 500 that may be displayed by the client user interface 406 in order to save information relating to the user 108 when the user 106 selects the link 301. As shown in FIG. 4, the screen includes data fields 501-506 for entering information relating to the user 108.

In one embodiment of the invention the client 112 is arranged to search the data store 126 with the details of the user 108 to see if an entry already exists for the user 108. The client engine 404 may control the client user interface 406 to only display page 500 if the details of the user 108 are not already present on the data store 126. If the details of the user 108 are already present on the data store, the client may be arranged to display an edit page 910 as shown in FIG. 10. The edit page will be described in detail hereinafter. In an alternative embodiment, if the client 112 determines that the user details are already stored on the data store 126 the client interface 406 may be arranged to display a page indicating that the listing already exists.

In accordance with an embodiment of the invention, the client user interface 406 is controlled by the client 404 engine to populate some of the data fields with the contact information stored in the local memory of the user device 102. For example the phone number data field 502 may be populated by the client 112 from the contact details stored in the local memory of the user device. The country data field 504 may also be populated by the client 112 using information which may be determined from the contact information stored in the local memory of the device 102 when the call was initiated. In one embodiment the client 112 may be arranged to recognise the country code prefix of the telephone number. Such an arrangement is disclosed in our U.S. application Ser. No. 11/416,378.

The user 106 may add further information to the information already added to the data fields by the client 112. For example, the user may add a business name to the business name data field 501. The user may also delete information or edit information in a data field already populated by the client.

In an alternative embodiment of the invention the data fields populated by the client cannot be deleted by the user 106.

In one embodiment of the invention the user 106 may also add other information to be stored on the data store 126 in addition to contact information. For example the user may add keywords in a keyword data field. The stored keywords may indicate the contact type, e.g. hairdressers, and can be used as searching criteria when searching information stored in the data store 126.

In a further embodiment of the invention the user may input a rating to the contact information to be stored in the data store 126. For example, if the contact information relates to a business the user may rate the quality of the service offered by the business. In one embodiment the rating may be given in the form of a percentage, 100% being a very good rating and 0% being a very poor rating. In an alternative embodiment of the invention the user may select a rating from rating options, for example the user may select one of excellent, very good, fair or poor. The rating information may then be stored with the contact details of the business and displayed with the contact details when the details for the business are retrieved from the data store 126.

In one embodiment of the invention the user is required to specify a rating before the contact information can be stored in the data store 126.

In a further embodiment of the invention the user 106 may also include a comment to be displayed with the contact information when the contact information is retrieved from the data store 126. The user may type a comment in the comment data field 508.

In accordance with a further embodiment of the invention the client user interface may also be controlled to allow a user to search for an entry in the data store 126.

A user may access a search entry page by selecting a search tab 601 (FIG. 5), selectable link or button provided by the client user interface. In response to the user selecting the search tab 601, the client engine 404 is arranged to control the client user interface to display a search entry page 602 as shown in FIG. 5.

A user may search the data store by searching for a type of contact in a particular location. The user may input the type of contact information required, for example ‘hairdressers’ into a contact type data field 603 in the search entry page 602. The contact type information entered in field 603 may be used to search the keywords stored on the database. The user may also input the required location, for example ‘London’ into the location data entry field 604. The user may then select a search button 605 to submit the information input in fields 603 and 604 to search the data store 126.

The search entry page may also be provided with a country data field 606. A default country may appear in the country data field 606 when the search entry page is displayed. The default country may be set as the country in which the user is located. This information may be preset by the user as part of the user profile information. The user may enter a different country in the country data field either manually or by selecting a country from a drop down menu.

The search entry page may also include a list of popular keywords that are stored on the data store 126. The popular keywords may be displayed as selectable links in field 607. In one embodiment of the invention the popular keywords displayed are popular keywords that are stored on the data store 126 for the country identified in the country data field 606.

In one embodiment of the invention the client application is arranged to search the data store 126 for a list of the keywords that are associated with the greatest number of entries for the identified country and to display the results to the search in the field 607 as selectable links.

In an alternative embodiment of the invention the client may be arranged to search the data store for a list of keywords that are associated with the most called entries for the identified countries and to display the results to the search in the field 607.

The user may search the data store by either selecting a keyword in the field 607 or by selecting the search button 605 to search the data store using the information input into data fields 603 and 604. When the user searches the data store by selecting a keyword displayed as a link, any information entered in data fields 603 and 604 may be ignored.

When the user submits information to search the data store 126 by for example selecting the search button 605 as described above, the client engine may be arranged to generate a search data store message in response to the users request to search the data store. The search data store message includes the contact information entered by the user in contact fields 603 and 604. The client protocol layer is then arranged to transmit the search data store message to the data store 126 via the network 104.

According to one embodiment of the invention, before the contact information is sent in the search data store message, the text of the content information input by the user in data fields 603 and 604 may be spell checked to ensure that the data store is searched using information that is spelt correctly. The spell checker may be implemented as an application running on the user device. The spell checker application may be arranged to detect the language setting of the client software installed on the computer in order to search for the correct spelling in the language setting of the client software.

The data store 126 is searched using the content information included in the search data store message sent from the user device. The search data store message also includes details of the user that transmitted the message. In one embodiment of the invention the user details transmitted in the search data store message are limited to details that facilitate the search results to be returned to the user that sent the search data store message. These details may include a telephone number of the user device or the user ID of the user. In an alternative embodiment of the invention the message may include user profile information such as the age or gender of the user. This information may be used to enhance the searching criteria for searching the database. For example the results of the search may be limited to content uploaded by users in the same age group.

The entries searched on the data store 1260 may be limited to entries matching the location input in the location data entry field. The entries stored on the data store 126 with content matching the content information provided in the search data store message are retrieved from the data store 126 and sent via the network 104 to the user device 102.

When the client engine receives the information from the data store 126, the client engine is arranged to control the client user interface to display the entries. The entries may be displayed on a results page.

FIG. 6 shows a results page 701 according to an embodiment of the present invention. In one embodiment of the invention only some of the entries received from the data store are displayed. The contact details for each entry displayed on the results page may be stored on a local memory of the user device 102. The user may select further entries by either selecting a page number 702 linked to additional results pages arranged to display further entries. Alternatively the user may scroll through the results pages using the left and right arrow buttons 703 and 704.

In a preferred embodiment of the invention the data store is arranged to sort the results into a particular order before the results are returned to the user device 102.

In one embodiment of the invention the results may be sorted by the relevance of the searching criteria. In this embodiment of the invention the results are sorted in order of the number of keywords stored for an entry that match the keywords entered in the content type data field 603 on the search entry page.

In an alternative embodiment of the invention the results may be sorted by order of the user ratings. In one embodiment the results may be sorted by the highest average user rating. In an alternative embodiment the results may be sorted in order of the entries having the highest percentage of ‘excellent’ ratings.

In another embodiment of the invention the results may be sorted such that the name of each contact is listed alphabetically.

In a further embodiment of the invention the results may be sorted by order of the number of calls logged to the user identified in each result.

In a further embodiment of the invention the results may be sorted according to how close the location specified in the contact details of an entry is to the location specified in the search as entered in the location data entry field.

In a further embodiment of the invention the results may be sorted according to whether a user specified in the contact details of an entry has requested to be listed above other entries in the search results. In one embodiment of the invention the network operator associated with the data store 126 may approach users specified in the entries stored on the data store to offer the user this option. A user may then pay to ensure that they are listed above other entries in the search results. According to this embodiment of the invention the data store may be arranged to store an indication that a user has requested to be listed above other entries in the search results. The search results may be sorted such that users that have requested to be listed in the search results appear at the top of the results list above any users that have not requested this option. In a further embodiment of the invention, the results may be sorted in order of how much the user has paid to be listed.

According to a further embodiment of the present invention the results may be ordered according to which of the entries have been created or commented on by users listed in a user's contact list. According to this embodiment of the invention, the entries that have been created or commented on by users included in the user's contact list appear at the top of the results list. According to one embodiment of the invention, the results from the data store 126 are sent to the user device 102 via the backend server 122. The contact list for the user is stored on the backend server. The backend server is arranged to compare the search results to the user's contact list. If the server 122 determines that there are entries that have been either created or commented on by the any of the users listed in the user's contact list, the server orders the results such that those entries appear at the top of the results list. The search results are then forwarded to the user device.

In alternative embodiment of the present invention the client 122 may be arranged to determine if there are any results that have been either created or commented on by the any of the users listed in the user's 106 contact list and to sort the results accordingly.

In a further alternative embodiment of the invention details of the user's contact list may be included in the content information provided in the search data store message. The results retrieved from the data store 126 may then only include results created or commented on by users listed in the user's 106 contact list.

In a further embodiment of the invention the search results may be ordered according to any combination of the above identified criteria. For example the location criteria may be combined with the call volume criteria, such that the results found for a particular location are listed in order of the most called entries.

This list is not exhaustive and is only intended as an example.

In an embodiment of the invention the user may select the criteria for ordering the results of the data store search.

In one embodiment of the invention, call statistics are monitored for each entry on the data store so that the data store may sort the results of a data store search by order of the most called. Call statistics may be collected by a Call Data Collector 130 (see FIG. 11). The Call Data Collector may form part of the data store 126. Alternatively the Call Data Collector 130 may be positioned at a separate location in the network to the data store 126. In one embodiment of the invention the call statistics relate to the number of communication events, such as voice calls or text communications, occurring for a particular user device. In another embodiment of the invention the call statistics may also include information relating to the duration of a communication, for example the duration of a voice call.

FIG. 11 shows the called user device 110 connected to a gateway 128. In this embodiment of the invention the user device 110 is connected to a separate network from the network 104. For example the user device 110 may be connected to a PSTN network. The gateway 128 enables the communication to be established between the network 104 and the network in which the user device 110 is located.

The call data collector 130 is arranged to count the number of communication events, such as calls, that occur for each user stored on the data store 126. The call statistics for each user listed on the data store are periodically sent to the data store 126 from the call data collector 130. On receipt of information transmitted from the call data collector 130, the data store 126 updates the entry for the called user with the call statistics.

In one embodiment of the invention the call data collector 130 includes a memory for storing a list of each called user device stored on the data store 126. The data store 126 transmits entry updates to the call data collector 130. The data store may transmit entry updates to the call data collector 130 each time an entry relating to a new called user is created, or at periodic intervals.

In one embodiment of the invention the call data collector 130 is arranged to count the number of calls made to a particular user device by counting the number of call data records (CDRs) that are generated for that user device. CDRs are records that are generated upon each calling event to facilitate charging in a communication network. CDRs are known in the art and will therefore not be described further herein.

In one embodiment of the invention the call data collector 130 analyses each CDR that is transmitted from the gateway 128 and checks its memory to identify if the CDR relates to a call made to a user device that is stored on the data store. If the CDR relates to a user device that is stored on the data store the call data collector increments the count for the number of calls to that number by 1.

In an embodiment of the invention only calls having duration above a predetermined time threshold are counted. In one embodiment only calls lasting 10 seconds or longer are counted.

In a further embodiment of the invention, calls from the same user to a number listed on the data store may only be counted once during a predetermined period. In one embodiment this period is 24 hrs.

In a further embodiment of the invention a plurality of call data collectors may be connected to the data store 126. In an embodiment of the invention all calls made from network 104 are monitored.

According to an embodiment of the invention the results page 701 may allow the user to search the data store again with a new criteria. Therefore the results page may also include a content type data field 603′ and a location data field 604.

When the results of the search are displayed, the client interface is arranged to allow the user to establish a communication with one of the called users listed in the results page. In a preferred embodiment of the invention the communication is a voice call. In alternative embodiments of the invention the communication may be a text message, instant message or another type of communication. In one embodiment of the invention the user may establish a call by selecting a call button 707 provided in relation to an entry 708 as shown in FIG. 6. On the selection of a call button 707 the client is arranged to establish a call with the contact 708 associated with the call button 707 using the contact details retrieved from the data store 126.

In one embodiment the user may store the contact details of an entry listed on the results page as a contact. If client interface receives a signal from the user to indicate that the contact details of a particular entry are to be stored as a contact the client is arranged to copy the contact details for that particular entry into a permanent memory store such as a ROM (read only memory) local to the user device 102.

The user may access the contact information entry page 500 from the results page by selecting a link 705 on the search results page 701. The user may decide to add new called user details when it is apparent that an expected contact, for example the user's favourite business, does not appear in the search results.

The user may access a details page for each entry displayed on the results page 701. The details page may be viewed by selecting a details link for a particular entry on the search results page. When the link is selected the client is arranged to retrieve details information for a particular entry from the data store 126. FIG. 8 shows an example of a details page 901 for a particular entry. The details page 901 may show the comments provided by other users that have previously called the contact.

In one embodiment of the invention the client user interface may provide the user with means for reporting any misuse of the data store 126 such as the storage of abusive comments or misleading information. As shown in FIG. 8 the details page 901 may include a selectable link 902 to allow the user to report any misuse of the data store. The user may select link 902 to access a page to allow the user to input any comments relating to the misuse. A ‘report misuse’ page 904 is shown in FIG. 9. As shown, the user may input a description of the misuse in field 905. Alternatively or additionally the user may indicate the reason for the misuse using the data field 907 that is populated using a drop down menu. The user may then submit the description to the operator by selecting a submit button 906. When the user selects the submit button 906, information included in the data fields on page 904 may be sent to customer services in a message.

In another embodiment of the invention the client user interface may provide the user with means for editing the information stored in relation to an entry on the data store 126. The details page 901 shown in FIG. 8 may include a selectable link 907 to allow the user to modify the information shown on the details page 901. The user may select the link 907 to access an editing page 910 shown in FIG. 10.

The editing page 910 includes data fields for updating the contact information for the selected entry on the data store 126. The data fields may include a business name data field 501′, a telephone number data field 502′ and location data fields 503′, 504′, 911, 912, 506′.

In a preferred embodiment of the invention, when the user accesses the edit page 910 the data fields are populated with the data currently stored on the data store. The user may then edit the information in the data field.

In another embodiment of the invention the user may not edit the information in the business name data field 501′ or in the phone number data field 502′. This prevents fraudulent use of the editing feature.

The editing page 910 may also be provided with a keyword data field 507′ for entering additional keywords.

Once the user has edited the information in the data fields the data may be sent to the data store to update the entry for that contact by selecting a submit button 914 provided on the editing page 910.

If the data store 126 does not contain any entries that match the searching criteria entered by the user in the content type data field 603, 603′, and the location data field 604, 604′, the data store may send a response to the client engine indicating that the search criteria did not match any listings. On receipt of this notification the client engine may control the client user interface to display a notification to the user that no results were found.

FIG. 7 shows an example of a page 801 displayed by the client user interface 406 when no results match the searching criteria.

The client user interface may be arranged provide the user with the option of searching an alternative data store provided by an authorised data store provider. A data field 803 is shown on the page 801 to allow the user to input a term to search another data store. According to an embodiment of the invention the client 112 may be arranged to populate the search data field 803 with the search terms previously input by the user on the search entry page 602.

While this invention has been particularly shown and described with references to example embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims. 

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled)
 6. (canceled)
 7. A system comprising: at least one processor; and one or more computer-readable storage devices comprising processor-executable instructions which, responsive to execution by the at least one processor, cause the system to implement a communication client for establishing communication events in a communication system, the communication client configured to perform operations including: displaying a search user interface associated with submitting a search request to a remote data store associated with the communication system; receiving, via a field entry box displayed on the search user interface, a keyword to submit to the remote data store; generating a search request message based, at least in part, on the keyword; sending, over a network and via the communication system, the search request message to the remote data store; receiving, over the network and via the communication system, one or more search results from the remote data store, the one or more search results based, at least in part, on the keyword; displaying, in a results user interface, the one or more search results in an order based upon a contact list associated with a user profile associated with the communication system; and initiating, over the network and via the communication system, a communication event using at least one search result of the one or more search results.
 8. The system as claimed in claim 7, said displaying the search user interface further comprising: receiving, over the network and via the communication system, one or more popular keywords from the remote data store; and displaying the one or more popular keyword searches on the search user interface, each respective popular keyword displayed with a selectable link operable to submit the respective popular keyword to the remote data store when selected.
 9. The system as claimed in claim 7, the operations further comprising: displaying a default location in the search user interface; and receiving, over the network and via the communication system, one or more popular keywords from the remote data store that are based, at least in part, on the default location.
 10. The system as claimed in claim 7, said displaying the default location comprising obtaining the default location from the user profile.
 11. The system as claimed in claim 7, said displaying the one or more search results in the order based upon the contact list further comprising: identifying each respective search result of the one or more search results that was created by a respective contact in the contact list, or contains a comment from the respective contact; and displaying each identified respective search result with a higher priority than other search results in the one or more search results.
 12. The system as claimed in claim 7, said generating the search request message further comprising including location information in the search request message effective to return search results associated with the location information.
 13. The system as claimed in claim 7, said displaying the one or more search results in the order based upon the contact list further comprising: receiving the order of the one or more search results from the remote data store.
 14. The system as claimed in claim 7, said initiating the communication event further comprising initiating a Voice-over-Internet Protocol (VoIP) communication event.
 15. A method comprising: connecting, over a network, to a communication system using a communication client associated with the communication system; displaying, using the communication client, a search user interface associated with submitting a search request to a remote data store associated with the communication system; receiving, via the search user interface, input to use in the search request; generating, using the communication client, a search request message based, at least in part, on the input and a user profile associated with the communication system; sending, via the communication system and using the communication client, the search request message to the remote data store; receiving, via the communication system and using the communication client, one or more search results from the remote data store; displaying, in a results user interface of the communication client, the one or more search results in an order based upon a contact list associated with the user profile; and initiating, via the communication system ad using the communication client, a communication event using a search result of the one or more search results.
 16. The method as claimed in claim 15, said displaying the search user interface further comprising displaying, in the search user interface, at least one of: a default location associated with the user profile; a text entry field associated with entering a keyword to submit to the remote data store in the search request; a text entry field associated with identifying a location to submit to the remote data store in the search request; or one or more selectable links, each respective selectable link of the one or more selectable links associated with a respective popular keyword to submit to the remote data store in the search request when selected.
 17. The method as claimed in claim 16, wherein the one or more selectable links are based, at least in part, on keyword searches stored at the remote data store that have the greatest numbers of entries associated with the default location or the location identified in the text entry field relative to other keyword searches.
 18. The method as claimed in claim 15, said generating the search request message further comprises: using the user profile to obtain age information, gender information, a user identifier, or a telephone number; and including the age information, gender information, the user identifier, or the telephone number in the search request message.
 19. The method as claimed in claim 15, wherein: said generating the search request message further comprises adding information associated with the contact list in the search request message to search the remote data store; and said receiving the one or more search results further comprises receiving only search results having an association with the contact list.
 20. The method as claimed in claim 15, said generating the search request message further comprising performing a spell-check on at least a part of the search request message.
 21. The method as claimed in claim 15, wherein said displaying the one or more search results further comprises displaying, in each respective search result of the one or more search results, a respective selectable control; and said initiating the communication event further comprises: receiving selection of one of the respective selectable controls; and responsive to receiving selection of the one of the respective selectable controls, initiating the communication event with a respective contact associated with the respective search result.
 22. One or more computer-readable storage devices comprising processor-executable instructions which, responsive to execution by at least one processor, are configured to implement a communication client for establishing communication events in a communication system, the communication client configured to perform operations comprising: displaying a search user interface associated with submitting a search request to a remote data store associated with the communication system; receiving, via the search user interface, input to use in the search request; generating a search request message based, at least in part, on the input and a user profile associated with the communication system; sending, over a network and via the communication system, the search request message to the remote data store; receiving, over the network and via the communication system, one or more search results from the remote data store; displaying, in a results user interface, the one or more search results in an order based upon a contact list associated with the user profile; and initiating, over the network and via the communication system, a communication event using a respective search result of the one or more search results.
 23. The one or more computer-readable storage devices as claimed in claim 22, said displaying the search user interface further comprising displaying, in the search user interface, at least one of: a configurable default location; a text entry field associated with entering a keyword to be submitted to the remote data store in the search request; a text entry field associated with identifying a location to be submitted to the remote data store in the search request; a selectable control to initiate a search of the remote data store; or one or more selectable links, each respective selectable link of the one or more links associated with a respective popular keyword stored at the remote data store.
 24. The one or more computer-readable storage devices as claimed in claim 22, the operations further comprising displaying, in the results user interface, at least one of: a selectable control to sort the one or more search results in an order based upon user rating; a selectable control to sort the one or more search results in an order based upon a most called criteria; and a selectable control to sort the one or more search results in alphabetical order.
 25. The one or more computer-readable storage devices as claimed in claim 22, the operations further comprising: using the user profile to obtain age information, gender information, a user identifier, or a telephone number; and including the age information, gender information, the user identifier, or the telephone number in the search request message.
 26. The one or more computer-readable storage devices as claimed in claim 22, said displaying the search user interface further comprising: displaying a navigation control; receiving selection of the navigation control; and responsive to receiving selection of the navigation control, navigating the communication client from the search user interface to a call-initiation user interface associated with the communication client. 